docs(CH-002): reconcile corpus with shipped TypeScript npm publishing#219
Merged
flemming-n-larsen merged 3 commits intoJul 19, 2026
Merged
Conversation
…publishing Open the change workspace for CH-002. The npm-publishing feature shipped before the Cliewen extraction (CH-001) and was never digested, so P-002/M-004 and CAP-013 still describe the OpenSpec-era intent rather than the shipped implementation. Serves P-002 / M-004 / CAP-013. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…rpus Reconcile P-002/M-004 and CAP-013 to the shipped implementation (docs only, no code change). The npmPack/npmPublish Gradle tasks and the live npm package @robocode.dev/tank-royale-bot-api@1.0.2 are the source of truth. - P-002: M-004 todo -> done with evidence; fix CAP-014 -> CAP-013; drop the never-built npmPublishDryRun and the "ACs tested" clause (that is M-002); plan active -> completed. - CAP-013 criteria: retire TNP-001 (dry-run, never built) and TNP-002/003 (NPM_TOKEN) as @Retired tombstones; remint TNP-005/006 for the shipped npmjs-api-key Gradle property; correct the requirement prose. TNP-004 kept. - CAP-013 design/README: correct to the shipped mechanism; note it is live. CAP-013 stays draft (promotion to active is the M-002 test-wiring door). - decisions/log.md: record the drop-dry-run and npmjs-api-key-over-NPM_TOKEN decisions. Delete the CH-002 change workspace (main must never contain /changes/). clue validate: OK. Serves P-002 / M-004 / CAP-013. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…xample Make the shipped credential mechanism clear for contributors: add a "Credential setup" section to CAP-013 design showing where npmjs-api-key lives (user gradle.properties, not the project file) and an example line, and noting it sits alongside the other publish credentials. Serves P-002 / M-004 / CAP-013. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
CH-002 — Reconcile the corpus with the shipped TypeScript npm-publishing work
Docs-only. The TypeScript Bot API npm-publishing feature shipped before the Cliewen extraction (CH-001) and was never digested, so the corpus still described the OpenSpec-era intent instead of what actually shipped.
clue validatewas green because the drift was semantic, not structural.Evidence it already shipped
npmPack+npmPublishGradle tasks inbot-api/typescript/build.gradle.kts/releaseskill invokes./gradlew :bot-api:typescript:npmPublish@robocode.dev/tank-royale-bot-api@1.0.2live on npm (modified 2026-05-18).npmrcgit-ignored (.gitignore:28)Divergences reconciled (decided with the maintainer)
M-004claimedtodofor done work →done; planactive→completed.M-004referenced a non-existentCAP-014→CAP-013.npmPublishDryRun(specTNP-001,M-004, design) was never built and is not needed —npmPackalready shows what would be published without uploading. Dropped from the spec.NPM_TOKENenv var; the shipped code uses anpmjs-api-keyGradle property (matches the Sonatype/PyPI pattern and the/releaseskill). Spec reconciled to reality.AC changes (clue-delta retire + remint)
TNP-001retired (task dropped, no remint).TNP-002/TNP-003retired (NPM_TOKEN) → remintedTNP-005/TNP-006(npmjs-api-key).TNP-004unchanged.Scope boundary
build.gradle.ktsis the source of truth.draft. Promotion toactiveneeds wired TNP tests — that is the separate M-002 door, not this change.Verification
clue validate→ OK (115 artifacts);clue validate --forbid-changes→ OK.NPM_TOKEN/npmPublishDryRunremain only inside the@retiredtombstones; noCAP-014anywhere.docs/decisions/log.md.🤖 Generated with Claude Code